Integration Capabilities

How to Integrate PHP with Tally using XML

Tally Interfaces – For Integration PHP Sample Code

How to Export data from tally using php?

<?php
    $requestXML = '<ENVELOPE>'.
      '<HEADER>'.
      '<TALLYREQUEST>Export Data</TALLYREQUEST>'.
      '</HEADER>'.
      '<BODY>'.
      '<EXPORTDATA>'.
      '<REQUESTDESC>'.
      '<REPORTNAME>Daybook</REPORTNAME>'.
      '<STATICVARIABLES>'.
      '<SVEXPORTFORMAT>$$SysName:XML</SVEXPORTFORMAT>'.
      '</STATICVARIABLES>'.
      '</REQUESTDESC>'.
      '</EXPORTDATA>'.
      '</BODY>'.
      '</ENVELOPE>';

$serverip = "localhost:9000";
$curl = curl_init($serverip);

curl_setopt($curl, CURLOPT_HTTPHEADER, array('Accept-Charset:UTF-8'));
$contentarray = array("content-type:text/xml;charset:UTF-8");
curl_setopt($curl, CURLOPT_HTTPHEADER, $contentarray);
curl_setopt($curl,CURLOPT_RETURNTRANSFER, 1);
curl_setopt($curl, CURLOPT_HEADER, 0);
curl_setopt($curl, CURLOPT_POST, 1);
curl_setopt($curl, CURLOPT_POSTFIELDS, $requestXML); // post the xml
curl_setopt($curl, CURLOPT_TIMEOUT, 300000); // set timeout in seconds
curl_setopt($curl,CURLOPT_ENCODING,"UTF-8");
$xmlstr = curl_exec ($curl);
if (!$xmlstr) die("No Response from tally: Curl");
// var_dump(curl_getinfo($curl, CURLINFO_CONTENT_TYPE));
curl_close ($curl);
echo ($xmlstr);

Tally prime is hanging, Not responding, not Opening

Reasons for Tally Prime is not responding

How to solve tally prime problem

Create Sales Order using xml request to Tally erp 9

How to Create Sales Order using xml request to Tally erp 9

<ENVELOPE>
<HEADER>
<TALLYREQUEST>Import Data</TALLYREQUEST>
</HEADER>
<BODY>
<IMPORTDATA>
<REQUESTDESC>
<REPORTNAME>All Masters</REPORTNAME>
<STATICVARIABLES>
<SVCURRENTCOMPANY>company</SVCURRENTCOMPANY>
</STATICVARIABLES>
</REQUESTDESC>
<REQUESTDATA>

<TALLYMESSAGE xmlns:UDF="TallyUDF">
<VOUCHER VCHTYPE="Sales Order" ACTION="Create">
<DATE>#fromdate</DATE>
<PARTYNAME>CustomerName</PARTYNAME>
<VOUCHERTYPENAME>Sales Order</VOUCHERTYPENAME>
<VOUCHERNUMBER>4</VOUCHERNUMBER>
<REFERENCE>14</REFERENCE>
<PARTYLEDGERNAME>A.R.AUTO PARTS</PARTYLEDGERNAME>
<BASICBASEPARTYNAME>A.R.AUTO PARTS</BASICBASEPARTYNAME>
<FBTPAYMENTTYPE>Default</FBTPAYMENTTYPE>
<PERSISTEDVIEW>Invoice Voucher View</PERSISTEDVIEW>
<BASICBUYERNAME></BASICBUYERNAME>

<LEDGERENTRIES.LIST>
<OLDAUDITENTRYIDS.LIST TYPE="Number">
        <OLDAUDITENTRYIDS>-1</OLDAUDITENTRYIDS>
       </OLDAUDITENTRYIDS.LIST>
<LEDGERNAME>A.R.AUTO PARTS</LEDGERNAME>
     <GSTCLASS/>
       <ISDEEMEDPOSITIVE>Yes</ISDEEMEDPOSITIVE>
       <LEDGERFROMITEM>No</LEDGERFROMITEM>
       <REMOVEZEROENTRIES>No</REMOVEZEROENTRIES>
       <ISPARTYLEDGER>Yes</ISPARTYLEDGER>
       <ISLASTDEEMEDPOSITIVE>Yes</ISLASTDEEMEDPOSITIVE>
       <AMOUNT>-3259.55</AMOUNT>
    <BANKALLOCATIONS.LIST>       </BANKALLOCATIONS.LIST>
       <BILLALLOCATIONS.LIST>       </BILLALLOCATIONS.LIST>
       <INTERESTCOLLECTION.LIST>       </INTERESTCOLLECTION.LIST>
       <OLDAUDITENTRIES.LIST>       </OLDAUDITENTRIES.LIST>
       <ACCOUNTAUDITENTRIES.LIST>       </ACCOUNTAUDITENTRIES.LIST>
       <AUDITENTRIES.LIST>       </AUDITENTRIES.LIST>
       <TAXBILLALLOCATIONS.LIST>       </TAXBILLALLOCATIONS.LIST>
       <TAXOBJECTALLOCATIONS.LIST>       </TAXOBJECTALLOCATIONS.LIST>
       <TDSEXPENSEALLOCATIONS.LIST>       </TDSEXPENSEALLOCATIONS.LIST>
       <VATSTATUTORYDETAILS.LIST>       </VATSTATUTORYDETAILS.LIST>
       <COSTTRACKALLOCATIONS.LIST>       </COSTTRACKALLOCATIONS.LIST>
</LEDGERENTRIES.LIST>

<ALLINVENTORYENTRIES.LIST>
<STOCKITEMNAME>01-0\11332W STD</STOCKITEMNAME>
<ISDEEMEDPOSITIVE>No</ISDEEMEDPOSITIVE>
<ISLASTDEEMEDPOSITIVE>No</ISLASTDEEMEDPOSITIVE>
<ISAUTONEGATE>No</ISAUTONEGATE>
<ISCUSTOMSCLEARANCE>No</ISCUSTOMSCLEARANCE>
<ISTRACKCOMPONENT>No</ISTRACKCOMPONENT>
<ISTRACKPRODUCTION>No</ISTRACKPRODUCTION>
<ISPRIMARYITEM>Yes</ISPRIMARYITEM>
<ISSCRAP>No</ISSCRAP>
<RATE>1100.05/Nos</RATE>
<AMOUNT>2200.10</AMOUNT>
<ACTUALQTY>2 Nos</ACTUALQTY>
<BILLEDQTY>2 Nos</BILLEDQTY>

   <BATCHALLOCATIONS.LIST>
        <BATCHNAME>Primary Batch</BATCHNAME>
        <INDENTNO/>
        <ORDERNO>5</ORDERNO>
        <TRACKINGNUMBER/>
        <DYNAMICCSTISCLEARED>No</DYNAMICCSTISCLEARED>
        <AMOUNT>2200.10</AMOUNT>
        <ACTUALQTY> 2 Nos.</ACTUALQTY>
        <BILLEDQTY> 2 Nos.</BILLEDQTY>
        <ORDERDUEDATE>27-Oct-2015</ORDERDUEDATE>
        <ADDITIONALDETAILS.LIST>        </ADDITIONALDETAILS.LIST>
        <VOUCHERCOMPONENTLIST.LIST>        </VOUCHERCOMPONENTLIST.LIST>
        <UDF:SHIPPEDBY.LIST DESC="`Shipped By``SpeedProduct``ItemPriceLevel`" ISLIST="YES" TYPE="String" INDEX="1">
         <UDF:SHIPPEDBY DESC="`Shipped By``SpeedProduct``ItemPriceLevel`">RETAIL</UDF:SHIPPEDBY>
        </UDF:SHIPPEDBY.LIST>
       </BATCHALLOCATIONS.LIST>

<ACCOUNTINGALLOCATIONS.LIST>
<LEDGERNAME>CAM SHAFTS SALES</LEDGERNAME>
<GSTCLASS/>
<ISDEEMEDPOSITIVE>No</ISDEEMEDPOSITIVE>
<LEDGERFROMITEM>No</LEDGERFROMITEM>
<REMOVEZEROENTRIES>No</REMOVEZEROENTRIES>
<ISPARTYLEDGER>No</ISPARTYLEDGER>
<ISLASTDEEMEDPOSITIVE>No</ISLASTDEEMEDPOSITIVE>
<AMOUNT>2847.77</AMOUNT>
</ACCOUNTINGALLOCATIONS.LIST>

</ALLINVENTORYENTRIES.LIST>

<ALLINVENTORYENTRIES.LIST>
<STOCKITEMNAME>01-0\12170W</STOCKITEMNAME>
<ISDEEMEDPOSITIVE>No</ISDEEMEDPOSITIVE>
<ISLASTDEEMEDPOSITIVE>No</ISLASTDEEMEDPOSITIVE>
<ISAUTONEGATE>No</ISAUTONEGATE>
<ISCUSTOMSCLEARANCE>No</ISCUSTOMSCLEARANCE>
<ISTRACKCOMPONENT>No</ISTRACKCOMPONENT>
<ISTRACKPRODUCTION>No</ISTRACKPRODUCTION>
<ISPRIMARYITEM>No</ISPRIMARYITEM>
<ISSCRAP>No</ISSCRAP>
<RATE>646.67/Nos</RATE>
<AMOUNT>646.67</AMOUNT>
<ACTUALQTY>1 Nos</ACTUALQTY>
<BILLEDQTY>1 Nos</BILLEDQTY>

<BATCHALLOCATIONS.LIST>
<MFDON>#fromdate</MFDON>
<GODOWNNAME></GODOWNNAME>
<BATCHNAME></BATCHNAME>
<DESTINATIONGODOWNNAME></DESTINATIONGODOWNNAME>
<INDENTNO/>
<ORDERNO>4</ORDERNO>
<DYNAMICCSTISCLEARED>No</DYNAMICCSTISCLEARED>
<AMOUNT>646.67</AMOUNT>
<ACTUALQTY>1 Nos</ACTUALQTY>
<BILLEDQTY>1 Nos</BILLEDQTY>
<ORDERDUEDATE>2 Days</ORDERDUEDATE>
</BATCHALLOCATIONS.LIST>

<ACCOUNTINGALLOCATIONS.LIST>
<LEDGERNAME>CAM SHAFTS SALES</LEDGERNAME>
<GSTCLASS/>
<ISDEEMEDPOSITIVE>No</ISDEEMEDPOSITIVE>
<LEDGERFROMITEM>No</LEDGERFROMITEM>
<REMOVEZEROENTRIES>No</REMOVEZEROENTRIES>
<ISPARTYLEDGER>No</ISPARTYLEDGER>
<ISLASTDEEMEDPOSITIVE>No</ISLASTDEEMEDPOSITIVE>
<AMOUNT>646.67</AMOUNT>
</ACCOUNTINGALLOCATIONS.LIST>

</ALLINVENTORYENTRIES.LIST>

</VOUCHER>
</TALLYMESSAGE>
</REQUESTDATA>
</IMPORTDATA>
</BODY>
</ENVELOPE>

குழந்தைகளுக்கான தூயத்தமிழ் பெயர்கள்

Tally Integration Using XML Read / Write

Tally Interfaces – For Integration

Tally communicates with the external world mainly using two Interfaces.
1.Tally ODBC Interface (Read Only)
2.Tally XML Interface (Read and Write)

Tally XML Interface Integration

XML (Extensible Markup Language) is the standard for information exchange with external systems. Tally.ERP 9 supports standardized message formats for Request/Response. Tally.ERP 9 can communicate with any environment capable of sending and receiving XML over HTTP.

Tally can act as an HTTP Server capable of receiving an XML Request and responding with an XML Response. The entire Tally Data can be made available to the requesting application. It is also possible for the application to store data into Tally Database.

Using the same interface, Tally has the capability to interact with a Web Service delivering Data over HTTP. In this scenario, Tally behaves as a client retrieving and storing data into an external database. The Web Service capable of handling Tally Request/Response serves as a layer between Tally and External Database.

Example : Tally - XML Integration
Tally - XML Request / Response

Let us consider different scenarios to understand the Request and Response XML structure.
Export - Request to Export Data and Corresponding response.
Import - Request to Import Data and the Corresponding response.
Execute - Request to Execute Action and Corresponding response.

Tally Export Data Using XML

Tags used for sending a request to export data from Tally.ERP 9.

contains the following:
Tag must contain value Export
Tag must contain value Data
Tag should contain the Name of the TDL Report
contains the following:

Tag can contain report settings like Company Name, Format, etc. as desired which should be enclosed within tag.

If the Report Name specified in the tag does not exist within Tally running at the specified port, the TDL defining the Report & other supporting definition needs to be described and enclosed within tag .

Example : Request for a detailed Trial Balance in XML Format from Tally.

<TALLYREQUEST>Export</TALLYREQUEST>

<ID>Trial Balance</ID>

</HEADER>

<BODY>

<DESC>

<SVEXPORTFORMAT>$$SysName:XML</SVEXPORTFORMAT>

In the above XML request, <HEADER> describes the expected result.

The value of the Tag <TALLYREQUEST> is Export which indicates that some information needs to be exported from Tally.
The value of the Tag <TYPE> is Data which indicates that the data needs to be exported from Tally.
The value of the Tag <ID> must be a TDL Report Name, if the previous Tag <TYPE> contains Data and Tag <TALLYREQUEST> contains Export. Any Report which needs to be exported from Tally can be specified within this Tag.
<BODY> Tag contains parameters, if any. Additional settings for the report like format required, company from which data is required, etc. can be passed within <STATICVARIABLES> Tag enclosed within <DESC> Tag. All variables are considered as Tag Names and their value are enclosed within these tags. For e.g., in the above XML, variables SVEXPORTFORMAT and EXPLODEFLAG are considered as Tags and their respective values $$SysName:XML and Yes are enclosed within. TDL Internal Function SysName is evaluated at Tally end and the response is being sent accordingly.

XML Response received From Tally

<DSPDISPNAME>Capital Account</DSPDISPNAME>

Tally Import Using XML

Tally can import data objects either in the form of a Master or Voucher.

<HEADER> contains the following

Tag <TALLYREQUEST> must contain value Import
Tag <TYPE> must contain value Data and
Tag <ID> should contain the Import TDL Report i.e., either All Masters or Vouchers.

<BODY> contains the following

Tag <DESC> can contain report settings like Company Name, behavior of Import in case of duplicates found; as desired which should be enclosed within <STATICVARIABLES> Tag.
Tag <DATA> must contain the XML Data Fragment within Tag <TALLYMESSAGE> that needs to be imported

Example : Request for importing Master data in Tally

<TALLYREQUEST>Import</TALLYREQUEST>

<IMPORTDUPS>@@DUPCOMBINE</IMPORTDUPS>

<PARENT>Bank Accounts</PARENT>

</LEDGER>

<NAME>Bangalore Debtors</NAME>

<PARENT>Sundry Debtors</PARENT>

</GROUP>

<NAME>RK Builders Pvt Ltd</NAME>

<PARENT>Bangalore Debtors</PARENT>

In the above XML Request, Create action is used. Any of the following system formulae can be used to choose the required behavior in case the system encounters a ledger with the same name. The behavior is for the treatment of the Opening Balance which is being imported.

DupModify specifies that the current Opening Balance should be modified with the new one that is being imported.
DupIgnoreCombine specifies that the ledger if exists need to be ignored.
DupCombine specifies the system to combine both the Opening Balances. Ideally, this option is used when Data pertaining to Group Companies are merged together into a single company.

On processing the above request for importing ledgers, the requested ledgers are created in Tally.

XML Response received From Tally.

</RESPONSE>

The above XML Response is a log of masters created, altered, combined, ignored or not imported due to some errors. It also contains information pertaining to the last Master ID imported. For Alteration and Deletion of Masters, the Object action needs to be Alter or Delete respectively.

For instance, in the above example,

Name of an existing ledger ICICI will get altered to HDFC.

In case of Deletion, following line suffices

Execute

Tags used for sending a request to Execute an action from Tally.ERP 9.

<HEADER> contains the following:

Tag <TALLYREQUEST> must contain value Execute
Tag <TYPE> must contain value TDLAction and
Tag <ID> should contain the Name of the TDL Action

Example : Request for Executing Synchronization in Tally

<TALLYREQUEST>Execute</TALLYREQUEST>

<TYPE>TDLAction</TYPE>

</HEADER>

</ENVELOPE>

In the above XML request, <HEADER> describes the expected result.

The value of the Tag <TALLYREQUEST> is Execute which indicates that some action needs to be executed in Tally.
The value of the Tag <TYPE> is TDLAction which indicates that some TDLAction has to be executed in Tally.
The value of the Tag <ID> must be a TDL Action Name. Any action which needs to be executed in Tally can be specified within this Tag.